Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | See parent post | Go Back
View Post [edit]

Poster: saitoh Date: Nov 12, 2009 9:24pm
Forum: etree Subject: Re: FTP uploads now working again!

ditto. Something's better than nothing.

Any word on examples of bad naming and good naming? If nothing else, just so those of us who use it have a better chance of not creating additional work. :-)

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or Staffgreenone Date: Nov 13, 2009 6:16am
Forum: etree Subject: Re: FTP uploads now working again!

The traditional naming convention is band abbreviation, date in yyyy-mm-dd format, and then any extensions you want to use. From the recent uploads, here's a good one:

http://www.archive.org/details/skce2009-11-08.nak300.flac16

skce is Steve Kimock Crazy Engine. 2009-11-08 is the date. nak300 is the (partial) source, useful for differentiating between multiple sources of the same show. And flac16 indicates the format of the show.

As for bad ones, there aren't all that many REALLY bad ones. But something like this is a bit harder to read:

http://www.archive.org/details/DakiniLiveAphanphest52009-08-22

Obviously, we know it's live, so "Live A" (sic) isn't really necessary. Also, it can be hard to read camel case when words are all smushed together. Something like dakini2009-08-22.phanphest5.flac16 would have been better. It's not horrible, it's just a little harder to parse visually.

Reply to this post
Reply [edit]

Poster: saitoh Date: Nov 13, 2009 7:14am
Forum: etree Subject: Re: FTP uploads now working again!

Ok, so what you're after us about is to make sure we create the directory properly. I didn't know if there was something special as well. Thanks for the clarification!

Terms of Use (10 Mar 2001)